- 4 minutes to read

Installing the IBM Integration Bus Logging Agent

Get started with seamless integration monitoring by installing the Nodinite IBM Integration Bus Logging Agent. This guide provides a step-by-step process to ensure a smooth installation, highlights unique benefits, and helps you avoid common pitfalls.

✅ Easy, guided installation process ✅ Secure and compliant with Windows Services best practices ✅ Integrates with Nodinite for centralized log management ✅ Comprehensive troubleshooting and support resources

Note

You must be a local administrator to have the right to install Windows Services

Before you begin

Make sure you comply with the prerequisites.

Step 1: Start the installer

Double-click on the MSI file to start the installation of the Nodinite IBM Integration Bus Logging Agent.
msi
Start the installer by running the MSI file.

Step 2: Welcome screen

On successful execution of the MSI file, a Welcome screen presents:
Welcome
The Welcome screen confirms the installer has started.

Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.

Step 3: Accept End User License Agreement

The Licensee is ultimately responsible for making sure Nodinite products are used according to the End User License Agreement. Make sure you have the assigned formal rights to install and perform modifications to the target environment before you continue installing any Nodinite products.
![EULA][10]
You must accept the terms in the License Agreement to continue.

Step 4: Custom setup

Select the components to install and select the destination path for the installation.
Custom Setup
Choose components and destination path. Default settings are recommended.

Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.

Step 5: Service Account Information

Enter the credentials for the Account to run the Nodinite IBM Integration Bus Logging Agent.

Enter credentials:

Domain: The name of the Domain the Server belongs to. If a local account is being used, use the name of the server or a . (dot) as Domain
User: The name of the account
Password: The password for the account
Domain service account
Enter the service account credentials for secure operation.

Insufficient Privileges

Error message when account information does not meet Prerequisites

Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.

Insufficient privileges Error message when provided account information does not meet the Prerequisites.
Insufficient Privileges
If you see this error, check account permissions and prerequisites.

If you get this message, the most common reason is that the account is not allowed to run as a service or is not a local Administrator on the server. Follow the guide How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Make sure to enter valid credentials!

Tip

Check the local event log if there are errors (both System and Application)

Step 6: Ready to install

Now all preparations are performed, Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Ready to Install
Here's an example of the Ready to install dialog

Step 7: Completed setup

The last step of the installation gives either a success or a premature exit.

Successful installation example:
Completed
A successful installation will show this dialog.

Failed installation example:
Premature exit
A failed installation will render a premature exit

Click the Finish button to Exit and quit the installer.

Step 8: Add Agent as a new Monitoring Agent Configuration

When the setup has been completed with success, your default text editor will open a text file named 'README.txt'. The README.txt file holds additional information that you need to add the agent as a Monitoring Agents. This file is [re]generated on each successful start.
README.txt
README.txt provides post-installation instructions.

Instructions on how to add the IBM Integration Bus Logging Agent as a Monitoring Agents are detailed in a shared article, click on the link below to learn more:

Step 9: Target the correct version of AMQMDNET.DLL

We have no idea what run-time version you are using. You may need to adjust the '%agent name%.exe.config' file to specify the exact version to use.

Please review the Troubleshooting guide for details.


Support

Contact our Support for additional guidance if you fail to resolve the installation problem.

Note

Additional information to aid the troubleshooting may exist in the Windows Event Logs.

Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite IBM Integration Bus Logging Agent exist in the Troubleshooting user guide.


Next Step

Configuration of the agent
Update
Uninstall

Prerequisites for IBM Integration Bus Logging Agent